Contained here is an illustrated, step-by-step guide to the installation and configuration. Home Router/Switch/Hub/Firewall help is here also to enable DCC chat and file sending (yeah, nekkid pictures!!!).

For starters

These instructions will be written from the stand point of a PC user with the mIRC program for IRC, but others (Mac + Linux) are similar in concept. You can get mIRC at http://www.mirc.com

This step by step illustrated guide has been tested many times over!

Ready? Set, go!

mIRC Software Installation


Below is an example that will connect you to the DALnet IRC networks and place you in the channel #abpp (no "m" at the end). NOTE: The 'backup' room is on RelicNet and is called #abppm (with "m" at the end).

mIRC DCC setup and Help

For Direct Client to Client (DCC) chat and send to work properly you need to tell mIRC how to get your correct internet IP address. Frequently mIRC has the wrong information on your IP and it breaks the DCC chat/send.

a) Go to mIRC Options - Connect - Local Info

b) Clear the Local Host and IP Address fields. If anything is in them mIRC will refill them with the correct info the next time you connect.

c) Check the Local Host and IP Address check boxes.

d) Select the Server under Lookup method (VERY IMPORTANT!!!).

e) OK to all and close mIRC.

This forces mIRC to get your public internet IP Address. You may have to update this information manually from time to time as the Server method depends on the server not being too busy to do the job (you might check it at one point and find it blank!). This is the IP Address mIRC will use when you do /dcc send or /dcc chat.

Tech note

Part of the confusion about DCC (Direct Client to Client) Chat and DCC File Send is that it's assumed that the IRC client is making an outgoing connection. mIRC (and all other IRC clients) creates a "Listening" socket on your computer. mIRC then sends a DCC Chat or Send request to the remote user in a CTCP packet. This packet includes the users IP address and the Listening socket port number. The remote user is the one that actually makes an outgoing connection to the initiating mIRC client (to the listening socket).


Routers, Hubs and Switches with Firewalls - IdentD and DCC issues

Identd - The Identify Daemon (IdentD) must be reachable on port 113 to allow the latest server authentication to work properly. Many Routers/Hubs/Switches handle this ports forwarding auto magically now and no action is required on your part. Many IRC networks will not let you join them without IdentD working properly. This port forwarding is done in your Router/Hub/Switch/Firewall control program. See your router's manual for exactly how to do this. One example URL is provided below at the end of this document in the section titled Other useful Resources.

DCC - Go to File, Options, DCC, Options, DCC Ports (this example assumes that you'll never send more than 10 files at a time. If you need more, set the "First" port number to a lower number. mIRC comes configured to use ports 1024 to 5000 for DCC which is too broad for many firewalls to allow. It's also not as secure as a narrower range (this example) provides.

Under DCC Ports:

a) Set First to 4990

b) Set Last to 5000

c) Click OK, and then quit mIRC.

On your Router/Hub/Switch/Firewall set port range to same ports as set above, and IP to the computer that you want to use mIRC DCC on.

Here is my setup on my ZyXEL hardware firewall. Note that there are two PC's setup for DCC in this illustration.

Here is my setup on my Kerio ver 2.14 software firewall. Tiny 2.15 is similar. Don't ask me about BlackIce Defender, Symantec Personal Firewall or Zone Alarm (Pro) as I don't/haven't used them.

Be sure to double check these settings as this is the single most common failure point!

Other useful Resources

A very well done illustrated guide to the above for a Linksys router titled 'mIRC and LinkSys Router (EtherFast 4-Port 10/100) Set Up Help' is found here: http://kareno.net/LinkSys/



Windows XP firewall help http://toidyman.net/xp-dcc/

A techie's dream guide: http://www.irchelp.org/irchelp/security/fwfaq.html and http://www.mirc.org/dcc.shtml

From K_b and L_v:

Active servers we have had good luck with:


Others may or may not be active at any given time. All are on port 6667 for those that need that info. Their website is http://www.dal.net/

Comments? Send them to click to e-mailHoople <hoople_ny@hotmail.com>

Last modified Thursday, March 06, 2003 7:33:03 PM